UCF STIG Viewer Logo

The Cassandra Server must utilize centralized management of the content captured in audit records generated by all components of the system.


Overview

Finding ID Version Rule ID IA Controls Severity
V-72673 VROM-CS-000210 SV-87305r1_rule Medium
Description
Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.
STIG Date
vRealize - Cassandra Security Technical Implementation Guide 2017-06-06

Details

Check Text ( C-72829r1_chk )
Review the Cassandra Server settings to ensure centralized management of the content captured in audit records generated by all components of the system are utilized.

At the command prompt, execute the following command:

# grep SyslogAppender /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml

If level is not set to "ALL", this is a finding.
Fix Text (F-79077r1_fix)
Configure the Cassandra Server to utilize centralized management of the content captured in audit records generated by all components of the system.

Navigate to and open /usr/lib/vmware-vcops/user/conf/cassandra/logback.xml.

Navigate to the node.

Add the following node to the node.


syslogServerHostName
AUTH
%-5level [%thread] %date{ISO8601, UTC} %F:%L - %msg%n


Navigate to the node.

Add the following to the node.